![]() 12/12/2019 at 15:17 • Filed to: None | ![]() | ![]() |
Android phones and BMWs are two of my favorite things. Except BMW has been on my shit list lately thanks to forgetting what steering feel is, and being one of the last car companies to add Android Auto to its cars’ infotainment screens. Oh, and their cars break. But mine hasn’t! (lately)
Hot on the heels of announcing that they !!!error: Indecipherable SUB-paragraph formatting!!! their idiotic cash grab scheme of charging a fucking subscription to keep your car’s Apple CarPlay activated, even though no other car company tries to pull that shit, BMW put out a !!!error: Indecipherable SUB-paragraph formatting!!! today saying they’re adding Android Auto to their cars. It’s a bit short on details. But there are some key points.
Starting in July 2020, all BMWs with infotainment systems running BMW OS 7.0 will ship from the factory with Android Auto.
Android Auto will be integrated into both the center dash infotainment screen and in the gauge cluster, plus heads-up display on cars equipped with the HUD.
BMW, despite being one of the last car companies to support Android Auto, is the first car company to support
wireless
Android Auto. So far that feature has only been available on aftermarket headunits. Not all Android phones support wireless Android Auto, but here’s a
!!!error: Indecipherable SUB-paragraph formatting!!!
.
The one wrinkle here is the press release doesn’t mention a wired connection at all. It’s unclear if there will be USB support in addition to wireless. I sure hope so, since the wireless Android Auto phone list is a short one. Those aftermarket headunits with wireless Android Auto also support a USB connection. We shall see.
Cars running BMW OS 7.0 that did not ship with Android Auto support will receive Android Auto through an OTA update, no visit to the dealer needed. The exact timing of this is fuzzy but supposedly it’ll happen close to that same July 2020 date.
Here’s my crack at a list of cars running BMW OS 7.0, scouring assorted forum posts and wikipedia pages and whatnot that I don’t feel like linking to.
2019-up G20 3-Series with Live Cockpit Professional (10.25" center control display + all-screen gauge cluster)
2020-up G30 LCI 5-Series
2020-up G32 6-Series (I haven’t confirmed this but since it shares most of its interior with the G30 5-series this would stand to reason, but now I’ve learned that the !!!error: Indecipherable SUB-paragraph formatting!!! . I guess that news came and went without my noticing. )
2020-up G11/G12 LCI 7-Series
2019-up G14/G15/G16 8-Series
2020-up G01 X3 with Live Cockpit Professional
2020-up G02 X4 with Live Cockpit Professional
2019-up G05 X5
2020-up G06 X6
2019-up G07 X7
2019-up G29 Z4
I’m guessing that Toyota Supra owners are out of luck, because when it launched, I remember multiple articles specifically mentioning that unlike the Z4, the Supra uses an older version of iDrive/BMW OS (probably 6), because Toyota prefers older technology “for reliability.”
No word on when this will trickle down to the various longitudinal-engine cars, i.e. Mini, X1, X2, 2 GC, etc.
Welcome to the motherfucking party, BMW. Here’s hoping you just forgot to mention that USB support.
UPDATE: Android Police !!!error: Indecipherable SUB-paragraph formatting!!! that they reached out to BMW about wired Android Auto support and BMW responded that there is no support for wired Android Auto. So basically, until wireless Android Auto becomes more widespread, you need a Pixel, or a Galaxy S/Note that’s an 8 or newer.
Not content with this news, I decided to look into any ways to get other phones to work with wireless Android Auto. I found !!!error: Indecipherable SUB-paragraph formatting!!! that shows how you might be able to kludge it together. It requires Android 9 Pie or higher, and this post suggests you need to be on the latest beta of Google Play Services, not the regular version.
On many phones, Google now hides the Android Auto app icon, so to get into the Android Auto app settings, you have to go to your phones settings menu, then view all your apps, pick Android Auto from the list, then scroll to the bottom where it says ‘additional settings in the app.’
Scroll to the bottom of the Android Auto settings, and tap 10 times on the version number at the bottom to enable developer settings. A little message will pop up on the screen saying you’ve successfully enabled them.
Hit the 3-dot menu in the top right and then select developer settings.
In developer settings, check the box for ‘add wireless projection to settings.’
Go back to the main Android Auto settings and then turn on the ‘enable wireless projection’ setting that has now appeared.
Reboot your phone and follow the headunit’s wireless pairing setup.
I followed this process on my Essential PH-1 and was able to at least access all these settings, but I don’t want to install a Google Play Services beta on my phone and don’t have access to a wireless Android Auto car or headunit anyway. Maybe I’ll try to go play with one at Best Buy or something and see if I’m able to get it to work without that Play Services beta.
I blame both Google and BMW for this. Google created the mess by only officially supporting wireless Android Auto on a very small list of phones. Seems like if it can be enabled on most phones with this bunch of hoop-jumping, it should be able to be supported by default. But BMW is just as much at fault for looking at the list of officially-supported wireless Android Auto phones and saying, “yup, we’re good with these.”
![]() 12/11/2019 at 13:08 |
|
So when I can finally afford a new M2 in 2025 I don’t have to pay for car play, neat.
![]() 12/11/2019 at 13:16 |
|
Hurray for Android Auto! Because honestly I prefer Android over iOS. I have owned both an iPhone and a Galaxy S and the Galaxy S had a better interface along with better customization.
![]() 12/11/2019 at 13:18 |
|
Ehh... no F-series cars, so I guess can’t just rip out an iDrive 7 unit and put it in mine. Guess I’ll stick with my HU_ENTRY.
![]() 12/11/2019 at 13:20 |
|
And no more yearly payment for car play lol
![]() 12/11/2019 at 13:31 |
|
I think, but don’t know for sure, that BMW OS 7 hardware is only compatible with CLAR platform cars. Not the older stuff.
So far BMW OS 7 is
limited to CLAR platform cars with Live Cockpit Professional (10.25" or larger center dash screen + full screen gauge cluster).
I suppose it mi ght be possible for someone to develop a retrofit for a pre-LCI G30 5-series, but not, say, an F30 3-series.
![]() 12/11/2019 at 13:44 |
|
Yeah, G30 retrofit is more likely. At most I can put in mine is an ID6 from an F30 LCI.
![]() 12/11/2019 at 14:05 |
|
I actually love the wireless CarPlay. Combined with wireless charging, I never have to plug my phone into the car at all. It’s a game changer. I’m sure the wireless Android Auto will start growing very quickly as new phones come out.
I have an iPhone so this won’t affect me, buuuut I have a 2020-up G01 X3 with Live Cockpit Professional and I think it’s actually on Version 6
![]() 12/11/2019 at 14:13 |
|
FINALLY!
Like you I’m a big fan of both BMW and Android, so I've been waiting for this announcement.
![]() 12/11/2019 at 14:18 |
|
Wireless CarPlay/Android Auto is certainly a good thing and better than having to plug your phone in. Especially since a lot of cars’ USB ports don’t put out a lot of juice and/or don’t support fast charging, so if you’re using the wireless connection to the car’s screen(s) you can use a proper fast charger for your phone when needed.
With only Google & Samsung phones supporting wireless Android Auto, the USB connection should be there to support all the other Android phones out there that are otherwise capable of running Android Auto. There are a decent number of aftermarket headunits with wireless Android Auto, and all of them also do Android Auto over USB.
BMW’s press release only talks about wireless Android Auto. One would hope that USB support is also there, but since it’s not mentioned in BMW’s press release , I don’t want to assume.
All BMWs with Live Cockpit Pro are on BMW OS 7. On the G01 it’s available as a standalone option, or as part of the Executive package. This is from the X3 configurator:
![]() 12/11/2019 at 14:40 |
|
I don’t think it will be there unless it has to be there in order to implement the wireless one. For CarPlay, you can’t plug it in to use the wired version despite an abundance of U SB ports.
![]() 12/11/2019 at 14:55 |
|
Not supporting wired CarPlay makes some degree of sense to since it works on any iPhone from the 5 on up running iOS 9 or higher.
Wireless Android Auto is only available on Google phones starting with the Nexus 6P & 5X from 2015, and on Samsung Galaxy S & Note phones starting with the 8, which are from 2017. But no other Samsung models.
While Samsung dominates the US Android phone market, LG and Motorola still have a decent-sized presence, and OnePlus is popular among Android enthusiasts.
Outside the US, there are all sorts of Android phone brands that are super popular. Even if you throw out Huawei and Honor with their current Trump Trade War difficulties preventing them from using Google services including Android Auto , there’s all the brands under the BBK umbrella (Oppo, Vivo, OnePlus, Realme), Sony, Asus, Lenovo, Nokia & Xiaomi . All of them are big, and none of them support wireless Android Auto but work fine over a USB connection.
Especially since BMW wants to sell a bunch of cars in China where BBK and Xiaomi are both huge, you’d think they’d want to at least try to support those phones via a wired connection.
![]() 12/11/2019 at 15:41 |
|
If there’s a new M2 on the CLAR platform with the S58 that would be very interesting indeed.
I’m honestly a little skeptical that the 2er coupe will continue, despite rumors that it’s in the works. Because the 2er coupe is unique among the luxo brands .
The 4er, C coupe, A5, RC and Q60 are all directly competing against each other and none of those other companies offer a smaller coupe like the 2er. Audi has the TT but that’s more of a Z4upra competitor than the 2er.
![]() 12/11/2019 at 17:42 |
|
Now if only Toyota would get to adding Android Auto support so I can ditch this iPhone and go back to a OnePlus.
![]() 12/12/2019 at 15:23 |
|
Not having CarPlay on my K900 is the one big omission from this car for me, and it doesn’t seem to be upgradable post facto like the Sedona’s is. It’s an entirely different system. I agree wireless CarPlay with charging would be a game changer, and I find myself wondering if there will ever be a good aftermarket fix I can get my hands on.
![]() 12/12/2019 at 16:17 |
|
I would assume that if you’re buying or leasing a new BMW, you probably have a newer phone as well. Wired support would be nice, but I don’t think its going to be much of an issue. The S8 has been out for 2,5 years already.
![]() 12/12/2019 at 16:19 |
|
Okay you just learned me how to enable wireless Android Auto, but do you know if it will work in any car with Android Auto, or does the car need to support wireless Android Auto?
![]() 12/12/2019 at 16:22 |
|
The issue is that only Google & Samsung phones officially support wireless Android Auto. Samsung phones bug the shit out of me, and while I like Pixels (and my wife has a Pixel 3a) I could see myself being more inclined towards a OnePlus than a Pixel. I’m also no fan of LG, but I do dig Motorola except for their crap track record with updates.
Outside the US, there are a ton of other Android phone brands that are extremely popular, none of which officially support wireless Android Auto. In those parts of the world where brands like BBK (Oppo, Vivo, OnePlus, Realme), Xiaomi, Asus, Nokia & Sony are widespread, this is leaving a lot of phones without the ability to connect to Android Auto in BMWs.
Of course, it’d be a non-issue entirely if Google made wireless Android Auto more widespread. Which, having played with the settings, doesn’t seem all that difficult for them to do if they were inclined.
![]() 12/12/2019 at 16:25 |
|
The car or aftermarket headunit needs to support wireless Android Auto. So far BMW is the only car company with wireless Android Auto support.
Enabling wireless Android Auto on the phone is only for making a non-Google/Samsung phone work wirelessly with a car/headunit that supports wireless Android Auto.
![]() 12/12/2019 at 16:29 |
|
Oh yeah, you’re right. I didn’t even look at the settings before I enabled developer settings. I have a Pixel 4 XL.
I wonder if I’ll ever be able to update the unit in my e-Golfs. It would be nice, because plugging in every time sucks ass.
![]() 12/12/2019 at 16:35 |
|
Yeah if you have a Pixel you don’t need to mess with any of the extra hoop jumping, it supports wireless Android Auto already.
I doubt you’d be able to add wireless Android Auto to your cars. It works over wifi, so if the car doesn’t have a wifi radio there’s no way to add the wireless Android Auto support.
![]() 12/12/2019 at 21:23 |
|
If prior to this week no car manufacturers supported wireless AA, it’s no shock that many phones don’t support it. Hopefully more auto manufacturers add wireless AA, pushing phone manufacturers to support it as well.
![]() 12/12/2019 at 21:35 |
|
I’m not sure if the phone manufacturers or Google are responsible for the lack of wireless AA support. It’s part of the AA phone app and there are hidden settings to enable it on phones that don’t officially support it.
While BMW is the first car company to support wireless AA, it's been around in aftermarket head units for a while now. Granted, the aftermarket stereo market isn't what it once was since so many cars no longer have DIN slots in their dashboard for installing aftermarket stereos, but still, this just seems like Google needs to get its shit together.